protect oac generated output - #3923
Closed
KuberSethi wants to merge 1 commit into
Closed
Conversation
Contributor
Storybook Preview🧹 Preview removed because this PR was closed. |
Contributor
Author
|
closing because the staging assembler already generates into a fresh isolated work directory, so output replacement safety is outside the RFC path |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
regenerating OaC output should never expose a partially written directory or destroy the prior output on failure
• generate into a sibling temporary directory
• reject protected and existing output paths by default
• replace clean output atomically and restore it after failure